Requirements for adopting software process lines

Requirements Engineering for Software Product Lines

The cost of fixing a requirements defect later in the development stage is much higher than the cost of identifying and fixing it in the early stages of development. In order to do this the system requirements must be properly identified, analyzed and reviewed early in the development process. Requirements engineering is such a process that focuses on discovering, analyzing, documenting and man...

Scoping software process lines

Defining organization-specific process standards by integrating, harmonizing, and standardizing heterogeneous and often implicit processes is an important task, especially for large development organizations. On the one hand, such a standard must be generic enough to cover all of the organization’s development activities; on the other hand, it must be as detailed and precise as possible to supp...

Adopting Software Product Lines: Approaches, Artefacts and Organization

Software product lines have received considerable adoption in the software industry and prove to be a very successful approach to intra-organizational software reuse. Contemporary literature on the subject, however, often presents only a single approach towards adopting a software product line. In this paper, we present an overview of different adoption approaches, different maturity levels for...

Goals and Scenarios for Requirements Engineering of Software Product Lines

Goal-oriented requirements engineering (GORE) approaches offer a natural way to capture similarities and the variability in software product lines (SPLs) development. Besides, they can effectively capture both the stakeholders’ objectives and the system requirements. From i* models, for example, it is possible to systematically obtain feature models. To complement the requirements specification...

Requirements engineering for systems and software product lines